Skip to content

Conversation

NataliaIvakina
Copy link
Collaborator

No description provided.

@NataliaIvakina NataliaIvakina force-pushed the dev-images-disaster-recovery-1 branch from 0a2fd7a to 6598d6c Compare October 1, 2025 11:24
@AnnaSjerling AnnaSjerling self-assigned this Oct 3, 2025
Copy link
Collaborator

@AnnaSjerling AnnaSjerling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the pictures are nice and that it will be easier to follow the guide with a more visual example. However, I feel like putting the pictures in the middle of the guide might be confusing, since the picture might not reflect the state for a user at all depending on how the disaster looks.

For example, if system database is not lost the pictures might be quite confusing when the user is on the section about fixing server availability. What do you think about having an additional section after the guide which goes through the example instead? Then we could also keep the guide itself more concise since we wouldn't need to remove the pop ups.

Also, do you think we should be more clear about the fact that the pictures only show how the databases are allocated. Because even though the allocations might be fine after the server step in our example, the last step is still needed to see that the databases are actually started and available.

What do you think? Pros vs cons?

@NataliaIvakina
Copy link
Collaborator Author

I think the pictures are nice and that it will be easier to follow the guide with a more visual example. However, I feel like putting the pictures in the middle of the guide might be confusing, since the picture might not reflect the state for a user at all depending on how the disaster looks.

I understand your concerns. Let me apply your suggestions to the page first so we can review the final result. Personally, I believe the images work well here -- they complement our disaster example effectively.
We cannot cover every possible disaster scenario. But our example includes the unavailable system db. A responsible user would not rely only on images; they would read instructions and notes.
I don't think that we have to make the guide concise. This page is not particularly long, and it doesn't hurt to scroll a bit. BTW, I'm afraid that users may miss our hidden guides when they quickly scroll the page.
It might be a good idea to ask a third person to take a look at the page and share whether the images make the guide clearer or more confusing.

@NataliaIvakina NataliaIvakina force-pushed the dev-images-disaster-recovery-1 branch from 8bd24c0 to cbaef33 Compare October 6, 2025 13:00
@neo4j-docops-agent
Copy link
Collaborator

This PR includes documentation updates
View the updated docs at https://neo4j-docs-operations-2619.surge.sh

Updated pages:

@AnnaSjerling
Copy link
Collaborator

AnnaSjerling commented Oct 6, 2025

That sounds like a good idea! Lets see what someone else thinks 😄

@NataliaIvakina NataliaIvakina removed the WIP label Oct 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants